Skip to main content

This is a new service – your feedback will help us to improve it.

Your data has issues

There is a problem

  • 1000 entries must have valid geometry
Reference Name Tree preservation order Uprn Address text Point Geometry Notes Felled date Entry date Start date End date
951 K39 217033784 GILSTON ROAD

Unexpected geom type

2025-01-03
952 Sep-83 217033746 GILSTON ROAD

Unexpected geom type

2025-01-03
953 Jun-90 217033715 GILSTON ROAD

Unexpected geom type

2025-01-03
954 35/97 217033748 GILSTON ROAD

Unexpected geom type

2025-01-03
955 15/00 217033746 GILSTON ROAD

Unexpected geom type

2025-01-03
956 Nov-72 217033801 GLEBE PLACE

Unexpected geom type

2025-01-03
957 Nov-72 217115065 GLEBE PLACE

Unexpected geom type

2025-01-03
958 Nov-72 217033824 GLEBE PLACE

Unexpected geom type

2025-01-03
959 Nov-72 217033826 GLEBE PLACE

Unexpected geom type

2025-01-03
960 Nov-72 217109988 GLEBE PLACE

Unexpected geom type

2025-01-03
961 Nov-72 217033831 GLEBE PLACE

Unexpected geom type

2025-01-03
962 Nov-72 217033853 GLEBE PLACE

Unexpected geom type

2025-01-03
963 Nov-72 217033854 GLEBE PLACE

Unexpected geom type

2025-01-03
964 Nov-72 217033856 GLEBE PLACE

Unexpected geom type

2025-01-03
965 Nov-72 217033861 GLEBE PLACE

Unexpected geom type

2025-01-03
966 Nov-72 217033872 GLEBE PLACE

Unexpected geom type

2025-01-03
967 Oct-85 217033864 GLEBE PLACE

Unexpected geom type

2025-01-03
968 Jan-76 217033836 GLEBE PLACE

Unexpected geom type

2025-01-03
969 K37 217107401 GLEDHOW GARDENS

Unexpected geom type

2025-01-03
970 Jan-95 217033984 GLEDHOW GARDENS

Unexpected geom type

2025-01-03
971 K43 217108077 GLOUCESTER ROAD

Unexpected geom type

2025-01-03
972 K43 217034642 GLOUCESTER ROAD

Unexpected geom type

2025-01-03
973 K44 217034657 GLOUCESTER ROAD

Unexpected geom type

2025-01-03
974 Aug-74 217034308 GLOUCESTER ROAD

Unexpected geom type

2025-01-03
975 Sep-74 217034441 GLOUCESTER ROAD

Unexpected geom type

2025-01-03
976 Sep-74 217034443 GLOUCESTER ROAD

Unexpected geom type

2025-01-03
977 Sep-74 217034444 GLOUCESTER ROAD

Unexpected geom type

2025-01-03
978 Sep-74 217034445 GLOUCESTER ROAD

Unexpected geom type

2025-01-03
979 Sep-74 217034446 GLOUCESTER ROAD

Unexpected geom type

2025-01-03
980 Sep-74 217034448 GLOUCESTER ROAD

Unexpected geom type

2025-01-03
981 Sep-74 217034449 GLOUCESTER ROAD

Unexpected geom type

2025-01-03
982 Sep-74 217034466 GLOUCESTER ROAD

Unexpected geom type

2025-01-03
983 May-84 217034446 GLOUCESTER ROAD

Unexpected geom type

2025-01-03
984 K58 217034713 GLOUCESTER WALK

Unexpected geom type

2025-01-03
985 Nov-97 217034690 GLOUCESTER WALK

Unexpected geom type

2025-01-03
986 Aug-72 217035373 GORDON PLACE

Unexpected geom type

2025-01-03
987 K58 217035390 GORDON PLACE

Unexpected geom type

2025-01-03
988 Aug-72 217035357 GORDON PLACE

Unexpected geom type

2025-01-03
989 K58 217035359 GORDON PLACE

Unexpected geom type

2025-01-03
990 Jun-74 217035610 GROSVENOR COTTAGES

Unexpected geom type

2025-01-03
991 23/75 217096797 GUNTER GROVE

Unexpected geom type

2025-01-03
992 23/75 217035730 GUNTER GROVE

Unexpected geom type

2025-01-03
993 19/96 217035731 GUNTER GROVE

Unexpected geom type

2025-01-03
994 23/75 217035757 GUNTER GROVE

Unexpected geom type

2025-01-03
995 23/75 217035763 GUNTER GROVE

Unexpected geom type

2025-01-03
996 23/75 217035768 GUNTER GROVE

Unexpected geom type

2025-01-03
997 23/75 217035780 GUNTER GROVE

Unexpected geom type

2025-01-03
998 23/75 217035785 GUNTER GROVE

Unexpected geom type

2025-01-03
999 23/75 217035793 GUNTER GROVE

Unexpected geom type

2025-01-03
1000 Oct-91 217035730 GUNTER GROVE

Unexpected geom type

2025-01-03

Showing rows 951 to 1000 of 1000

How to fix this issue

Your dataset is missing the geometry column.

The Tree guidance explains how to fix the issue:

geometry

The boundary of the tree as a single polygon or multipolygon value. All points in the polygon must be in the WGS84 coordinate reference system.

If you’re providing geometry in a CSV, geometry should be in well-known text (WKT).

You must provide a point or geometry for each tree. You may provide both.

Example: MULTIPOLYGON (((1.188829 51.23478,1.188376 51.234909,1.188381 51.234917,1.187912 51.235022...

If you’re providing geometry in a GeoJSON, GML or Geopackage, use the associated geometry format.

How to improve Royal Borough of Kensington and Chelsea’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL